We require wlfullclient-10.x.jar file in our web application(deployed in Tomcat) to invoke some external services which deployed in web logic server.
The problem is wlfullclient jar has servlet related class, hence tomcat server excludes this jar while deploying the app, but we need this jar since we are using other classes available in wlfullclient jar.
I suspect that you are going to have to forgo using Tomcat and set up another WebLogic server. Either that or not employ WebLogic-specific features in your client webapp.
Even if Tomcat didn't exclude the j2EE core classes from the deployed application you would be on fragile ground, since Tomcat's internal implementations of those classes is quite different from (and incompatible with) WebLogic's. Only the interfaces are portable. Mixing the two would be a major train wreck.
As far as I know, you shouldn't have to include a WebLogic-specific library to invoke WebLogic EJBs remotely, nor, for that matter, to use JMS. So as long as you stick to the J2EE standard, you may not need wlfullclient.
Customer surveys are for companies who didn't pay proper attention to begin with.