Or, maybe nobody thought to add such functionality. 
Personally, I'm for it as long as the user understands the risks involved when using a remote connection. (See what I said about unlocking wallets.)
I greatly appreciate your answer and your patience. As I already said, I'm quite sure I know what I'm doing and the risks involved. My objective is to create an internal intranet service where we could manage different accounts (wallets) for employees.
Our server is well secured and I like to be able to manage wallets via an internal service that will "talk" to Armory via RPC (which will talk to bitcoind).
I love the fact that Armory is using bitcoind as a full node, but the downside of bitcoind is the lack of dynamic wallets management. Adding a new wallet requires shutting down the bitcoind, adding a wallet entry to the bitcoin.conf manually, and starting the bitcoind manually. this is quite annoying.
I find Armory to be very well designed, but I need the GUI functionality of managing wallets to be done via RPC including adding fresh new wallet for an employee instead of doing that manually via GUI.
So I think this feature will be great for us and others!
