Not a bug, but as $selectedTabId is no longer used to match the selected tab, the arguments and description for the Navigations_Tab code event listener should be updated to reflect this.
@Mike A while ago, wasn't the selected tab id changed to be determined by the route? I removed the $selectedTabId argument from my navigations tab listener and the proper tabs are highlighted when they, or one of its sub-menu links is clicked.
I just tried removing the $selectedTabId from the Resource Manager template listener, and the tab still works as intended, so I'm not sure why it is still a required argument.