Honestabebread:
I don't believe the Active Notifications are causing excess battery drain, however. When comparing a Droid Mini and a Droid Maxx, I began noticing that the Droid Maxx was "pulsing" far more often than the Mini. As it turns out, the Mini doesn't seem to pulse unless it is disturbed - a moderate change in ambient light exposure, detectable physical movement, or a new notification seem to be the only things that trigger the Active Notifications - otherwise they just don't show (likewise, if the phone believes it's in your pocket, the notifications don't show). This is in contrast to the Maxx, where the notifications pulse at regular intervals without any form of sensor stimuli required to trigger them. It appears this was done specifically to reduce how often the notifications are displayed (which is basically, not that often - the phone ends up displaying them pretty much only at times when you're about to flick the phone on anyway), and thus reduce battery life concerns. My battery life was very good yesterday - lots of screen on time, GPS, streaming music, generally playing around with it for no reason, picture and video taking and usage in direct sunlight - the battery finally died after just shy of 14 hours. Today will be a better test as the battery has had a few good cycles now and should be pretty accurate. It is becoming clear, however, that the Active Notifications implementation on the Droid Mini are more of a novelty as the LED is the only thing that's going to notify you in most situations.
Finally, it's worth noting that one of the first things the phones did when I powered them on was to download an update to the Active Notifications. It's possible that this update made the modifications listed above specifically to address battery concerns with the (what we believe to be) LCD screen. I would assume that if a Mini did not receive this update, it could very well be an issue, but this is pure conjecture on my part.