Well, for me SESSION scope is not fine-grained enough. I want the User entity to be removed when the user logs out. I think it's a performance pro because my webapp offers many features which don't require to be logged in. Any others sharing my opinion? Or is it best practice to have a User entity session-scoped? Anyway, I can think of other use cases where it is useful to put an entity in conversation scope for a while and remove it when it is no longer needed. For me this is just good design, isn't it?! :-) Greetings, Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022486#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...