Fixed double firing of onConnect().

Fixed issue where the onConnect() event in a SocketIOClient handler is fired twice for a single connection: once from the run() method in WebSocketClient, and once from the onMessage() event in SocketIOClient. It would seem that the later is redundant.