The only option you have is the recommended J2EE client approach:
Which is where you break your client into 2 piecs.
1. A standalone client like you are used to
2. A jar that is deployed on a jboss instance running on the same system as the standalone client
It is possible to strip jboss down into a very minimal set of services to provide this functionality.
To me your usecase sounds a good candidate to a servlet based server implementation.