I'm concerned about impressive stack traces. Considering SFSB as backing beans for JSF we need to take into account a lot of interceptors introduced by EJB3 (JBOSS implementation) and Seam. So I'd like to raise question about possible optimization on that matter. I believe that hundred calls costs a lot. There is another side of this question. I realized that I like to back JSF page by SFSB with extended persistence context in a Seam conversational context. It allows me to forget about LazyInitializationException and display on the page (or pageflow) whatever I want. But having investigated a lot I realized that number of interactions between JSF and SFSB is pretty big. Every bean dereference leads to impressive work of interceptors. And now I understand that I want either approach of omitting numerous interactions with SFSB or optimization in JBOSS and Seam when only required interceptions are made. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007972#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...