Well, first you already have 150 concurrent sessions, so that's the same. The additional state holder that Seam providers, the conversation, is not used unless one of your 150 users executes a stateful conversation. Just browsing stuff isn't a stateful conversation, for example, but editing something would likely be a conversation. What you have to calculate is simply more memory consumption for the sessions in general, because this is where JSF stores its state (although in an intranet you _might_ want to store that on the client in a hidden form field), and where Seam stores its conversation state (if you don't use stateful EJBs - but it's really the same memory issue). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039338#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...