I can't find the particular commit/issue for Webkit, but the authors expressed that they were using the timer limitation to prevent non-foreground tabs from sucking up CPU time. Others came along with workarounds (scheduling 1000 timers at 1ms intervals that will each fire once per second) and the authors said if they saw something like that being put to practice, they'd have to re-evaluate their method for limiting javascript usage by background threads.
http://news.ycombinator.com/item?id=347359
Plura ran into trouble because they built a pay-for-grid computing platform where the nodes were unsuspecting users:
http://pluraprocessing.wordpress.com/2009/08/24/our-response...
Personally I'd like to see a SETI@Home or Folding@Home in the browser first.
https://bitcointalk.org/index.php?topic=9042.msg130817#msg13...