As I keep saying,
yes it is possible to create something similar to a webapp that is Free software. [0]
But, let's take a look at the actual technologies behind the "web":
1. A naming system/transport protocol
2. A document markup language
3. A virtual machine for sandboxed code.
(2) is user-friendly (PoLP). But creating a Free app implies ignoring the defining "web" features of (1) and (3)!
If a single user is the only one accessing a given name, then that naming system has basically been made irrelevant. (If multiple users are accessing a given name, then per HTTP only one is in control of that name, and thus we deviate from free software).
If a user controls updates to the code and (in theory) audits it, then the primary purpose of the sandbox (executing random third-party specified code) is gone. The battle-hardened sandbox is nice for security, but the functionality is otherwise indistinguishable from any other language.
Why should such an app be called a "webapp" if it does not utilize most web features?
> based on your previous statements you're assuming a multi-user registration model with a centralized database you find on every commercial site which is a pre-requisite to monetization
I am not assuming this - I am noticing that a large majority of released projects are. Either due to lack of developer thought about repudiating "web" assumptions, or deliberate corporate "free-washing".
Platform defaults end up defining the culture of a platform. A good question to ask yourself - if you were designing a Free calculator app and wanted to show a friend, would you send them the files you're editing and they'd set it up on their own httpd to try it out, or would you end up sending them a URL to your server and thereby undermine their freedom?
[0] Although as I've said, many of those PHP etc apps are not actually Free - for instance the blog platforms.