from a guess at the fact they specifically say they use the existing same origin policy, they cant, but the confusion is cleared up with a simple test, I will check tomorrow
I haven't tried it myself with web sockets yet, but I've done some experiments with XHR+CORS (almost the same protocol, except for different names of the response headers) and it does work cross-origin on recent Gecko and WebKit browsers.
UPDATE: Ran a quick test using the current Google Chrome beta for Linux and standalone.py from Google's mod_websocket, and successfully opened a cross-origin WebSocket connection, just as described in the spec. mod_websocket will authorize requests from any origin by default; there's a sample handler included that shows how to reject cross-origin requests on the server.
This is basically the same as the Cross-Origin Resource Sharing spec, another W3C spec supported by some current browsers:
http://www.w3.org/TR/access-control/
> "The first three lines in each case are hard-coded" (referring to the origin)
No, the three hard-coded lines of each handshake part come before the origin headers: