Overall looks good, and pretty straight forward I think. Only thing I'd add is that it might be nice to add a helper like the following that would just let the users pass a map of functions as the public API:

(defn ws-listener [{:keys [on-open on-message on-pong on-close]}]
  {:ring.websocket/listener
   (reify wsp/Listener
     (on-open [_ sock] (on-open sock))
     (on-message [_ sock mesg] (on-message sock mesg))
     (on-pong [_ sock mesg] (on-pong sock mesg))
     (on-close [_ sock code reason] (on-close sock code reason)))})

That's a good idea, and I've already implemented it 😉 . The ring.websocket namespace extends the Listener protocol to cover a map of functions.

awesome, otherwise just ping me whenever new Ring version is out with ws support and we can push this change out along with it then. :)