When StatefulTreeCache gets a callback from StatefulRemoveInterceptor telling it an @Remove method has been invoked, it only removes the bean context from the clustered cache if the bean doesn't have any live nested children. Problem is, it also doesn't replicate the bean context. Effect of this is that the other nodes in the cluster are made aware that the parent bean has been removed.

This problem occurs because the StatefulRemoveInterceptor handles the @Remove after the call has already passed through the StatefulReplicationInterceptor.

Solution is to have StatefulTreeCache.remove() replicate the context via a TreeCache.put() if the presence of live nested beans prevents it removing the context via a TreeCache.remove().