It's amazing how much work has gone into researching this problem and as far as I can tell, none of it done by Apple, who actually has the fiduciary responsiblity for the problem; it's an Apple problem. Lots of work, novel setups, novel solutions which mitigate the problem for a brief period of time, Wake on LAN is a particular problem for me because it's not just a failure of wake on LAN, it's shown up as a failure of wake on an active application that has a timer (that would be Indigo, a home control application that has worked as long as the application is running) that only executes a command a few times per day.
Another application, Splashtop Streamer, a remote access server has a setting to tell the computer never to go to sleep, which doesn't seem to work on Mountain Lion. I still had to go into System Preferences and specify in the power management system to tell the system never to sleep (that works, but now my Mac is always fully on and sleep mode is pretty much useless and thus irrelevent).
Since it's Apple hardware, Apple OS, Apple network (with Apple firmware), it's not exactly like having an HP computer running Microsoft Windows and we have HP pointing fingers at Microsoft and vice versa. We have Apple users begging Apple to resolve the problem and point some fingers at themselves. This failure to wake from program control (which includes wake on LAN) is a major problem since it effectively disables the power management for any of us who are not using a Mac merely as an interactive endpoint device.'
APPLE! WAKE UP! APPLE? Oh, it's not waking up...