Please when you post in the forums do not copy and paste from MS Word because this puts a bunch of invalid xml and style into your post and makes the page invalid. Please use a plain text editor instead or write directly in the editor of the forum.
Regarding un-installation, there are very good reasons we do not do this kind of thing in mojoPortal even though other apps may do it.
You can remove features (so they are not available in the site) from the web ui under Administration > Advanced Tools > Features, but if you visit setup page they will come back so you also need to delete the features from under /Setup/applications/[featurename] using an ftp user with more permissions and this will prevent the setup page from re-configuring them.
Some applications (the other 2 popular .NET CMSs for example) allow you to install features by uploading a .zip file and it unzips it and puts all the files where they need to go, like dll files go in the /bin folder. One of them even allows you to install from over the web and it will download the feature from a remote server and install it.
The reason we do not design it to work like that is because of security. It is a very bad idea for the /bin folder to be writable by the web process and even worse if application code is designed to download more executable code from the internet and install it. This opens up an attack surface that could be exploited for remote code execution. I'm sure the application logic in these systems is designed to protect from that by controlling it by roles and permissions who can install code. However that means that application code is the only protection. It is much better to have additional protection by file system permissions that do not allow the web code to install any executable code. Therefore, while it might seem like a convenient feature to be able to install like that, it is not a good design from a security point of view. In my opinion, installing a feature should be done by ftp using a more privileged user than the one that the web application runs as. So applications designed like that cannot be hardened for security. These same applications (I'm not naming them but you can guess) also make the Web.config writable because they modify it from web code during setup, this is another really bad idea that opens up vulnerability.
No folder that has executable code or allows executable code should ever be writable by web code. Any folder that allows file uploads should be configured to not allow scripts or executable code. So we don't want code in mojoPortal to be able to add executable code to the file system nor to delete executable code from the file system.
I am fully aware that we do not have the same convenience as some of these other apps for installing/uninstalling features but I think it is more important to have good security and to not design/develop in a way that opens up attack surface. Those apps require the entire web site to be writable from web code, a very bad idea in my opinion. As with many things in life, just because you can do something does not mean you should do it.
So the feature you get in mojoPortal is the ability to sleep well at night knowing that your site is not designed this way and is less vulnerable to hacking than these other systems that have convenient installation from the web page.