The limited scheduled task abstraction that we provide is not really to restrict what you can do so much as it is to provide a cron-like service in an environment where cron isn't available. That might need a bit more explanation...
On PythonAnywhere, you're not operating in your own virtual server -- our virtualisation layer is much simpler. This has the huge advantage that we can let you "burst" and use much more resources than we could guarantee to provide day-in, day-out at our current prices. But it does have the disadvantage that we have to reimplement certain things.
The situation with processes is similar, though it's made more complicated by the fact that we abstract away the location where your processes are running, so even if we did provide ps so that you could see what was running on a specific server, there's no guarantee that the thing you were looking for (especially if it was started from a scheduled task) would be running on the server you were running ps on.
So, what we need to do is either change our virtualisation system (which I think would be a mistake) or provide more cron-like (and ps-like) features of our own. We're planning to do the latter.
Which leads me on to the question... which features of cron should we look at emulating? I see that someone was asking for days-of-the-week scheduling in the web2py cron thread, so would that be a good one? Or are there other things that would be more useful?
For a ps equivalent, I think it's pretty clear that we need to provide a page inside PythonAnywhere where you can see a definitive list of everything you have running, with the option to kill them. This could aggregate across all of the servers in our cluster. Is there anything else we'd need in that?
Suggestions, as ever, very much welcome :-)