If the SFSB is packaged with the war and the dependencies are working correctly, the SFSB should be undeployed locally before the war. So disconnecting the SFSB cache from the cluster before undeploying won't help. This remove call will just go to another node anyway. The ClusteredSession.expireSession(...) method that gets called when the manager clears sessions takes 'notify' param that controls whether the HttpSessionEvent gets set. Currently that's 'true', probably should be 'false'. Probably should be configurable, with a default of 'false'. It's more complicated than that; i.e. that 'notify' flag is used for other purposes as well; need to examine the semantics of those usages. The most complicated part is the need to ensure the event eventually gets emmitted. i.e. if the last node in the cluster is shutting down, then the session really is being destroyed. Can you open a JIRA for this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164770#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...