On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes.  This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.

This has the consequence of leaking memory for abandoned sessions.

This also impacts replication caches that contain passivated entries.