The problem is that when you get more and more tabs going, Firefox's single-threadedness becomes more and more painful. When one misbehaving tab locks up (or crashes) the whole browser, that's bad.
I hate it when people who know how to disable them don't do it and complain about it. It is really Ubuntu's fault for bundling an addon that is not compatible with multiprocesses.
I have lots of tabs open all the time, it's not really an issue for me most of the time. But it's true that every now and then it happens that something goes wrong and CPU consumption in Firefox stays way up. (I blame plugins/extensions though.) In such a case, I don't mind killing the process and restarting Firefox to remedy that.
It is similar to Chromes memory usage, add one tab after another and you will hit memory wall pretty fast (100 tabs?), with firefox 1000 tabs is not a problem.
That's why I switched back from Chrome after using it for a month few years ago.
Now I would switch because Chrome is the new IE, some developers don't test on Firefox, they say "just use Chrome", no WAY.