So the point here is to build the view in such a way that there is no need to re-add listeners because the html that triggers an action (say a button) is separate from the html where the result of the action is displayed (e.g. <div id="view">) ?
yes, that's how I would do it. SAM is like MVC, it does not mandate a particular implementation. The constraints are only on the semantics.
V = S( vm(M.present(A(data))), nap(M))
where S, vm, A and nap are pure functions
After that you can use for instance pub/sub for implementing the present method, cycle.js looks wonderful too.
Works with HTTP (kind of, like MVC2), WebSocket (better), Polling, ... Meteor would work well
It's really up to you. All I want to emphasize is that the need for frameworks is greatly reduced compared to MVC because of the structure of the pattern.