Improve logging in unhandled websocket exceptions

Currently, if an exception is thrown in an @OnMessage method in a websocket server, the exception is not printed anywhere. It would be ideal to catch this exception and report it back to the end user (developer) so that they can be aware of their runtime issues and fix them.

At least from my experience, these are development problems, and are indicative of something wrong rather than an actual exception.