This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Ultimately, your application may fail. As I have done in the past, especially if you require those parameters for your jsp to display the right content. In my case, every time I load the JSP page, nothing happen, if I refresh the page, it worked. Problem was I had all my implementation in the JSP page. Don't do it
EJB fits in Model layer(or a layer which interacts with data i.e. database),JSP is essentially there for rich web UI.
Calling EJB from JSP is really a bad design.
It makes code hard to debug & maintain.Also, In software development we should design application with entities defined with certain responsibilities. JSP should be used only for "View" i.e. Presentation layer & should not be "Overloaded" with responsibility of "Model"(which inturn talks with data later).
Also, when you mix these layers, application can't be extended with additional features that may come in furure(Requirements are ever changing also people want that applciation should support additional features at variuous stages).