Try inserting paths to your web application libraries into JBOSS_CLASSPATH variable in the bin/run.bat file (on Windows) or bin/run.sh (on *NIX).
This will probably require you to deploy your WAR file in expanded form in JBOSS, or to separate out the libraries into a folder of their own accessible by JBOSS.
Also note that doing so may render parts of JBOSS unreliable (those parts that depend on the JBOSS version of these libraries).
You will need to restart JBOSS to activate the new classpath.
Thanks for your advice, but unfortunantly, that doesn't seem to work. In fact, JBoss won't even start when that's the case, due to major class conflicts.
A temporary work-around has been to make a web application which basically spawns it's own Java VM in order to do any "dirty" work, and an admittedly crude hack to communicate across VM's.
If you or anyone else has any other ideas, I'd still sure like to know, especially since the above solution doesn't seem very "clean" to me.
Thank you! That information is exactly what I need.
P.s. It's pretty cool that the 3 reply to this post came from the C.T.O of JBoss... if I were superstitious, I would say that this means I'm destined for great doings. :)