Stateful session beans are more resource intensive than stateless session beans. The stateful implementation remains bound to the client that creates them until the client calls the remove method or EAServer removes the instance because it has timed out. You can minimize the performance impact of using stateful session beans by following these recommendations:
Always call the remove method Code your clients to call remove so that EAServer knows when the instance is no longer needed.
Configure a passivation timeout Configure this setting as described in “Passivation timeout for stateful components” The timeout ensures removal or passivation of component instances when the client crashes or the end user walks away from their desk.
Configure the maximum allowed instances If clients activate too many instances at once, the server can run out of memory. To prevent this, set a limit on the number of instances that can be active using a thread monitor. See “Thread monitors”.
