remove workaround for chrome datachannel id issue

This removes the workaround implemented by this pull request:
https://github.com/uProxy/uproxy-lib/pull/61

I tested this by hammering the SOCKS server on Chrome 39. I was able to create a few thousand datachannels without observing the issue.

@mollyling is this the issue you mentioned?