Wallet Connect Websocket issue on iOS

*Note*: Filing this before doing due diligence

Evidently when a browser on iOS is backgrounded, unless there is some media playing, the browser is essentially paused and unloaded from memory.

When the browser is foregrounded again the websocket connection will _retransmit_ the same frame.

I believe the retransmitted frame/messages is what is causing issues with iOS 5.x and "solved" by turning off the experimental NSUrlSession setting on iOS.

If possible, we should investigate what it might take for the Wallet Connect Bridge to ignore a retransmitted frame/message.