Nope - not if you put them in the Conversation or Session context, and change their state while they are there. HttpSession does not do dirty checking. You would have to call Context.set() each time you change the object. JavaBean components in Seam 1.1 have special facility for making them cluster-safe - namely the Mutable interface. Entity bean components do not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978212#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...