I was actually thinking of ways to optimize this even further, for instance having the OnUpdate script fire only when you enter combat and niling itself when dead = 0 and not InCombatLockdown. Unfortunately this idea won't fly, because it doesn't account for random events that can lead to deaths, for instance someone taking falling damage, or failing @ frogger in Patch/Mimiron or even dying to some combat situation, without necessarily putting you in combat. Unfortunately, continuous scanning of the raid roster seems to be the way to go (unless I'm terribly missing something).
Since mots plugins are now going the LDB route, it doesn't make sense to call everything Fubar_xxxx. Besides, if you use the search/find functions on either Curse or WoWI, you could probably find this. You'll need Broker2Fubar to display this in Fubar, until Fubar decides to support LDB natively. Sigh.