When an entity gets included in the initial state of two group replicables (due to getting removed from the first group after it has been replicated, and getting added to the second before it has been replicated) and the first group finishes streaming after the second group, both of these groups get loaded into the scene on the client at the same time. This causes the client to see an entity in two groups at the same time -- since the RPC event buffer for the first group isn't replayed until after both groups have been added to the scene.

The root cause of this is multiple replicable streaming groups can get merged on the client depending on the order in which they finish loading. Instead of merging replicable streaming groups instead the client should ensure each group is fully loaded into the scene, with all buffered RPC events replayed, before subsequent replicable streaming groups are loaded into the scene. Ideally those subsequent replicable streaming groups will still get prepared into a staging scene asynchronously though.