Plus, it is much better for over-all performance since some websites switched to an interface that polls for updates in the background.
Of course I know I'm not a typical user, so I wouldn't really argue against this being an option that is off by default. But it would very much hurt my user experience if it weren't available at all.
I just wanted to mention my viewpoint (started writing it before I saw the other replies), since I find it an important improvement. For example, I won't use Chromium regularly besides testing things in it, because it would be way too painful for me.
In the "General" preferences in Firefox 13, if you have "Show my tabs from last time" selected, there's a checkbox for "Don't load tabs until selected".
In Firefox 15 and later, the checkbox is in the "Tabs" pane so it's always accessible: http://zpao.com/posts/making-restore-on-demand-accessible/
However, I'm of the opinion that options are bad UX too (until you find them :). It's better when the experience is just good. I know that's asking a lot... but I think it's possible with some combination of the ideas mentioned in this discussion to automatically do the right thing for most users.
[1] It would be interesting to define a heuristic for what qualifies as a "simple" webpage. Perhaps anything that doesn't do any JS setTimeouts or websocket connection creation would count? It'd likely be best to just leave it to the web server to declare "simplicity" of a page as a header, the same way companies can declare "recyclable" on boxes. One would wonder if any company would bother to use this if it meant their own tab would seem slower-to-reload than their competitors', though...