Compile fix.
Fix possible assertion during active TCP connects and a possible connection leak.

- Sometimes `bufferevent_socket_connect` will invoke the `onSocketEvent` callback synchronously instead of using the event loop. The resumeTask failed in this case. See also http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/14474/

- When an `Error` (vs. an `Exception`) was thrown within an incoming TCP connection handler, the connection wasn't actively closed, possibly resulting in a permanent socket leak