I think "multiple independent PeerConnection" will enable, in some way, multi-party chat. And over each PeerConnection you can have multiple streams (e.g. audio/video and data stream for something else).

They are planning to allow multiple peer connections per page but the current implementation doesn't allow more than one. Trying to create another webkitPeerConnection00 object will throw an error or it will error or be unresponsive when you attempt to use it.

But yes, p2p multi-party chat is very possible with WebRTC. Unfortunately, there's additional overhead as each client has to send it's stream to each other client instead of having a server to multiplex it. It also means the app developer's costs are lower and of course if you want you can still PeerConnect to a server that then acts a multiplexing hub.