Hi Paul On Wed, Mar 26, 2014 at 3:57 PM, Paul Ferraro <paul.ferraro(a)redhat.com&gt; wrote: You'd probably need expiration events for in-memory entries first: https://issues.jboss.org/browse/ISPN-694 This has been in discussion for a while, but I'm not sure it will make it into 7.0. It may require expiration to be coupled with eviction, to avoid duplicate expiration events. (I'm sure Sanne would be happy about this, because we would stop checking if the entry is expired on every access.) There is a reasonable workaround for this, or at least there will be once we have expiration events: only make one entry mortal, and use its expiration listener to remove all the other entries in the group. Funny, I was just looking at the Cache.evict() javadoc and it seems we haven't removed this line yet: Important: this method should not be called from within a transaction scope. TBH I think storing the session as a DeltaAware would be a better fit for this requirement. Either way, I don't think it will make it into 7.0. I don't see this as a priority, you could just invoke a distributed task that calls cache.evict(k) on each node. Internally, we'd probably use a command, but the effect would be the same. I think Mircea already had a chat with Davide about implementing this in Infinispan. However, I don't see a lot of scope for optimizations over what you have already implemented for sessions. This sounds like a bug more than a feature request, it should definitely be included in 7.0.