Plug WebSocket.terminate timeout leak

If a caller tracks server connections (`WebSocket`s) on their own and cleans them up manually right before calling `WebSocketServer.close`, the calls to `terminate` (one from the caller closing the connection manually, and one from the server loop doing it) can happen so quickly that the internal state is `WebSocket.CLOSING` in both calls.  

This means that the second call will over-write the first call's `this._closeTimer`.  That means a timer gets leaked, and holds the program open for 30s.  Not a huge problem, but a confounding one.

This one-liner will prevent that.  The "right" answer is probably to update the state machine, but as far as I can tell, this timeout is the only collateral in this scenario, so the one-liner should be sufficient in practice.
Update the `save` flag with two hyphens, not three :)
Merge pull request #404 from david-davidson/npm-cli-flag-typo

Update the `save` flag with two hyphens, not three
implement permessage-deflate extension
add tests for permessage-deflate
Correct year in history
Merge pull request #410 from woutermeek/patch-1

Correct year in history
fix an error on Node 0.8
Merge pull request #409 from nkzawa/feature/permessage-deflate

Support permessage-deflate extension
[dist] 0.6
Merge pull request #342 from toejough/patch-1

Plug WebSocket.terminate timeout leak
[fix] Disabled perMessageDeflate
[dist] 0.6.1
[dist] 0.6.2