In a previous post, Getting CRUDy with Meteor, I wrote about a way to abstract your event handling so that you didn't have to handle routine events in every single template. The original solution came from my Meteor application EtherPOS. The solution was a bit complex, I think partially, because it was so early on in both Meteor's progress and my own Meteor development progress.
Recently, during a massive upgrade of EtherPOS, I further abstracted my event handling into an even simpler structure through the use of nested templates. This has resulted in more readable code, easier maintainability and easier debugging.