I have several JSF pages that are initializing and accessing ManagedBeans that are not even used on that page. This is creating a really hairy problem for initialization. I either have to make them all session scope and continually make calls to re-inialize or take the performance hit of having them read large amounts of data from the DB whenever they decide to initialize.

Some of the managed beans being accessed are not even defined on the page in question.

I have done some optimization based on comments related to multiple calls to getters, but I still have the issue that I have a very specialized (and expensive to initialize) bean that is getting called when I don't want it initialized.

Any insight into why/what JSF calls might do something like this.

I have a very complex page making use of JSTL, Tomahawk and standard JSF tags.

I could include code, but its very complex and sensitive in nature.