Did they originally NOT run things on the same machine? Otherwise the WebSocket would be local and incur no cost.
replies(4):
The basic point is that WebSockets requires that data move across channels that are too general and cause multiple unaligned memory copies. The CPU cost to do the copies was what cost the megabuck, not network transfer costs.