Do you cache the EJB home and then reuse it to create multiple beans? If not, just don't configure your SFSB as clustered, as I don't think having it be clustered is doing anything for you. If that simple approach doesn't meet your needs, you can try replacing the clustered bean cache with the non-clustered one. E.g. in jboss.xml: | <jboss> | <enterprise-beans> | <session> | <ejb-name>nonreplicatedsfsb</ejb-name> | <configuration-name>Non-Replicated Clustered SFSB</configuration-name> | <clustered>true</clustered> | </session> | </enterprise-beans> | | <container-configurations> | <container-configuration extends="Clustered Stateful SessionBean"> | <container-name>Non-Replicated Clustered SFSB</container-name> | <instance-cache>org.jboss.ejb.plugins.StatefulSessionInstanceCache</instance-cache> | <persistence-manager>org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager</persistence-manager> | </container-configuration> | </container-configurations> | | </jboss> | Note I've never tried the above. And I cut-and-pasted the xml from a few different places, so their might be some mistakes. But that shows the basic idea -- set up a special configuration that overrides the "Clustered Stateful Session Bean" config defined in conf/standardjboss.xml. The special config uses the non-clustered SFSB caching. At the top I'm showing an example of configuring a particular bean to use the special configuration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190306#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...