"ALRubinger" wrote : SLSBs *do* have state, as the instance is returned to the Pool after use. Therefore invocation-specific data should not be kept in instance members of a SLSB. Thanks, Andrew. This makes good sense. However, if I only run one single facade method, and previous old state doesn't bug me (all variables are re-initialized before used), can such "temporal" use of fields be justified? Imagine I have a chain of methods inside a SLSB. a calls b, b calls c, c calls d, etc. Facade method receives a parameter. I need to use that parameter down the chain of execution. Should I put that parameter in each method declaration? Ouch ... Doesn't look very appealing, don't you think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171104#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...