FYI, here are a couple of the main relevant threads I found from last year: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85462 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=83772 The first one has a discussion at the end re: the proper scope of ref sharing with a POJO attribute in a web session. Basically, pojos for a webapp are stored at /JESSION/hostname/contextpath/_JBossInternal_. So refs can be shared across sessions. With BR, sharing across sessions is not a good idea, as different cluster nodes can own the sessions, and thus fight over ownership of the shared pojo. But, we don't enforce that restriction. One possibility is to enforce that restriction by storing pojos at /JESSION/hostname/contextpath/sessionId/_JBossInternal_. If we did that, my initial plain cache get of /JESSION/hostname/contextpath/sessionId/ will cause gravitation of everything, and the problem goes away. (I realize the above is very FIELD-repl use case oriented; not generic. I'm mostly just thinking out loud and doing a bit of a data dump here.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056970#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...