About reactive WebSockets, I wrote a client and server library which lets you consume WebSocket data streams in a reactive way using pure async/await syntax (no callbacks, no Observables): https://asyngular.io

It encourages the use of IIFEs as a way to declaratively isolate parallel async operations from serial async operations. Also it shifts control to the data consumer instead of the producer; this should reduce the likelihood of memory leaks.