Will bad things happen if my app nests a few levels down via cascaded "self callPage" and then the user clicks a link that takes them directly back to the top level page where they may begin to cascade back down again? I'm concerned about resource usage when the call stack is not properly unwound via "self return".