A wild guess
See title: this is a wild guess...
My guess is that this is some fuck-OOPery. There's a timer somewhere bunging "send DNS multicast" events into a queue. When the device is asleep, because this is a typical fuck-OOP, instead of the timer ceasing to add events to the queue, some handler merely suspends processing the queue so the queue lengthens and lengthens and lengthens. And then the device wakes up...
Yes, you can achieve the same stupidity in non-OOP languages. It's just that people are less likely to make mistakes like that in non-OOP languages because you have to have some sort of understanding of what's happening instead of putting Lego™ blocks together according to some "pattern."
If I were to have an even wilder guess, I'd say Java.
OK, I'm being cynical and ranting non-justifiably against all things OOP merely because I hate OOP. It's Monday. Maybe I'll be in a better mood tomorrow.
Biting the hand that feeds IT
