Well, since you need to keep conversational state somewhere, that would only be possible with a SFSB. I don't see how SLSBs can do the same? Sure, you can hold your conversation state in some other components and inject/outject them on your SLSB on every method call, but why would you when there are SFSBs? The EntityHome etc. components that come bundled with Seam are equivalent to conversational SFSBs, they are implemented as conversational Seam-managed JavaBeans because not everybody who wants to use them has an EJB 3.0 container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018985#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...