Right,

IMO the objective of the two approach are very similar, but authorization_listener is __per__ url which can be useful sometimes. 

I will however add a notice on the authorization listener where it's said that this listener cannot handle security which are directly in the controller or in template, and point the user to the direction of user-context for this use-case.

I will reintegrate this listener.