Server side exception classes are exposed to EJB clients

Currently we are passing all exceptions from the server directly to clients. We should have a strategy encapsulate "system exceptions" so the client does not require server exception classes on the client.

I propose we serialize the full exception class, the exception message, and the exception stack trace separately. This will double the size of the exception on the wire, but will allow us to attempt to deserialize the exception and if that fails, create a new replacement exception using the message and stack trace.