Track clones will all fire events when being ended, muted...
The order of the events is visible from web applications but the spec is not really clear about this.

It even allows one track to be muted and not a clone, since UA can set muted on a track granularity and not source granularity.

I would think this has no bing interop impact but the spec should in theory provide guidance there since this is JS observable (maybe fire events by order of creation of tracks?)