The Loathsome OOM Killer

So, every now and then, Mozilla starts getting hungry for memory, consumes all my physical memory, devours all the swap, rolls over and dies a bloated mess. This isn't too big a deal, as it's been doing this for years, and it rarely catches me by surprise. What does disturb me is that sometimes other processes sacrifice themselves to save the browser. My IRC session with my ill-gotten Operator status. The Great American Novel, unsaved in my editor. My X session, with each of the windows laboriously adjusted just so.

So, my question is: Is it possible to mark certain processes as out-of-bounds for the Out-Of-Memory Killer?