Hi Sergio,
1) I don't think so. When the connection is made it does a one time fetch of the session data that is kept in memory for the duration of the WebSocket connection. You can not write back to the storage.
2) There were two reasons for this: A custom session handler had to be used in order to access the data as the native php session options weren't accessible and the other reason is that because a Ratchet application handles multiple connections global variables are not scoped to one user so $_SESSION is un-usable; Symfony offered both an OO Session API and multiple storage methods.
I began working on re-writing the Session component on the weekend which will allow for refreshed reads, writes, non-blocking I/O, and a more modular structure with Symfony as an adapter but able to support other session handlers and frameworks. Unfortunately, I don't have a timeline for this component at the moment (it's hard ;)).