Hi Justin.
Unfortunately I don't have any time to look at it in more detail at the moment. But to deploy classes to the database (it sounded like that) feels still like the wrong approach to me (it does already in jbpm 3). Actually with jBPM 3 we created some kind of classloader-Registry as MBEan in JBoss to access different JBOss-Classloaders of different deployments from the central engine. I described that back in time here: http://www.bpm-guide.de/2008/11/14/jbpm-deployer-status-and-sourcecode/. Unfortunately the pictures seem to have vanished, I hope it is understandable anyway...
Maybe that gives a new idea.
Good luck
Cheers
Bernd