With the current code, the moment the pojo has been evicted and you call one of it's set/get methods, the cache interceptor will be removed, so the indeterminism is already present, even before the suggested change. If we're gonna fix the indeterminism at some point, we'll need some option to cope with both scenarios, since there might be users already relying on this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227114#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...