The js is certainly processor-intensive; the client polls every 2 seconds for updates. Search is also done in the client, which can get kinda slow. We'll look into optimizing that code a bit more, but we are trying for "rich client," which involves a bit of client-side processor tradeoff. I'm hoping that the newest wave of JS engines (sunspider, v8, whatever's in FF3.5) will also increase the adoption of rich web clients.
As others have said, it could use a different design. Specifically, the fonts look kind of strange (letters don't have a consistent height) in my browser (Firefox 3.0 on Linux). Also you might want to streamline the javascript, as it looks like it caused firefox to use a lot more CPU.