Deleted child entity not represented on another client

Hello.
I use DevForce 2012 in a distributed system using several Windows clients and a server.
Suppose the model has 2 entities with 1:N relation, A and B. A has a collection of 3 B's (navigation prop).
Each client loads A and all its B's using include list.
One client deletes one child B and saves changes to the server.
Then another client re-queries A.Inlude(Bs) using DataSourceOnly strategy.
Unfortunately, the other client still gets A with 3 B's rather than only 2 ones.
I also tried EntityReferenceLoadStrategy.Load and explicit Load() via EntityMetadata.
I understand it's because the deleted B remains in the cache of the other client; But I expect that the explicit load will remove it from there.
A total cache clear is not an option to me, and a manual removal for each such scenario is tedious.
Any ideas?

Thanks for your quick reply.
Now I see that it does work with 1:N relation (while using EntityReferenceLoadStrategy.Load), but not in N:N relation between A and B.
That means, if client1 performs a.Bs.Remove(b) and client2 loads A.Include(Bs), it still gets all the Bs, i.e. the stolen entity remain in its cache.
As a workaround, I thought to use save interceptor on the server, detect the changes and publish to the clients the entity keys that have to be re-fetched;
But in N:N relation I found no indication to the removal. A and B are at unchanged state, and the linking table is abstracted away as we know.
There must be some indication in EntityManager to entity removal in N:N relation. What is it?
Or should I take a different approach?