With web apps becoming more complex by the day, having the ability do all the heavy work on a remote server and stream the resulting “webpage” back to a weak receiver with little processing power will unlock new ways of doing things: one can imagine a very slim screen that, as mentioned in the thread already, is running the full Adobe Suite from this remote server.
Great battery life and responsiveness without needing an expensive GPU / CPU on the device itself.
Say that you just made a big frontend change to your website. Before you release it, you can open it on the last 10 major versions of desktop and mobile Chrome/Firefox/Safari/etc. Any rendering failures that you find are the sort of bugs that can be very frustrating to debug from occasional user contacts.
But it can be tricky to automate the detection of visual bugs. And what if you have to make a few clicks and execute some javascript to get to the screen that you want to test?
Anyways, that's one use of browsers-as-a-service.