You dont need ejb-link in web.xml.
Hope you are clear that an ear should have .jar to keep all the class files and .war to have all
jsp's
i'll give you an example.
suppose i have example.ear in the end for deployment.
its structure would be something like-
3 folders
ejb-app.jar
META-INF
web-app.war
now my ejb-app.jar has my class files in a folder hierarchy
and a META-INF which has jboss.xml and ejb-jar.xml
The META-INF has an application.xml which defines the link between war and jar. which is as follows--
<application>
<display-name>My Application</display-name>
<module>
<web>
<web-uri>web-app.war</web-uri>
<context-root>/</context-root>
</web>
</module>
<module>
<ejb>ejb-app.jar</ejb>
</module>
</application>
The web-app.war has again 2 folders namely
JSP having all jsp's and WEB-INF which has and tld's along with struts-config.xml and tiles-def.xml if you are using
struts and tiles.
and ofcourse web.xml
web.xml should only have servlet mapping.
hope this helps.