Any one else have these problems with Mavericks 10.9.3?

Question

I've observed the following wiith Mavericks:
If the system has multiple user accounts on it, it will start, erratically it seems, running background processes with those user IDs. With com.apple.IconServicesAgent eating up sometimes nearly 300MB of memory, this can get to be a memory wart hog.
It appears to be using about 20% more memory.
The fans are coming on a lot more, indicating the CPU is being taxed.
Erratically and inconsistently "losing" external drives on sleep.
High levels of memory compression when there was none before.
I reported on item #1 last night with this link:
https://discussions.apple.com/message/25807061#25807061
I monitor system activity with a tool named Performance Probe which shows the memory usage the old way (pie chart) and then bring up Activity Monitor to get the deteails. After rebooting one time, Performance Probe showed nearly 3GB out of 4GB of memory in active use right after booting, this used to report less than 2 GB. The exact same thing happened as in the link above, but in this case every single user account on the system had an instance of cfprefsd, launchd, distnoted, and com.apple.IconServicesAgent with IconServicesAgent being the "Grandaddy" of memory consumption. I used Activtiy monitor to kill all the launchd processes in the unused (not logged into) accounts followed by the rest and they never restarted.
Observation: For some reason the OS seems to erratically decide to launch or not launch all these other user accounts. Sometimes  Activity Monitor will just show me and the normal system accounts on the sytem, other times it appears to be more or less a crap shoot as to what processes have been started under what users name.
For item 2, normally 10.9.2 was showing about 2.1G of RAM in use now it's running about 2.4-2.5GB. All that I typically have running is Safari and Mail and thats when I noticed this increase.
Item 3 is just an observation, but it tells me the CPU is doing a lot more work to do the same things it did before.
For item 4, I'd heard of this before but I'd never seen it, until now. If external drives are connected to the system and the system goes to sleep, when you wake it up the OS will say the drive and it's volumes were incorrectly ejected. This happens erratically on USB drives. To simulate it I set the sleep interval at 3 minutes and let it go to sleep several times. Sometimes the drives would be there, sometimes I'd get the unmounted message. I should also note that the first time I rebooted Mavericks after the update it didn't see my Firewire external drive but has since then.
I noticed item 5 after using Safari and Mail for a while. The system more or less came to a crawl, fans came on high speed, Perfomance Probe was showing about 3GB of RAM used (RED) with the other 1GB completely blue, which means it's not active but swappable. This was weird because I'd never seen the system "pegged" like this. Usually there's free memory showing up. I opened up Activity Monitor to get the details and it showed that about 1GB of RAM was compressed. This has never happened before. The only things in use were Mail and Safari, and I'd guess I was probably using Safari to go to weather.com.
I have never had or witnessed any of these problems before.

Answer 1

An update:
For item 1, I suspect that when the other accounts were used, the users left them in the modes to reopen applications etc when restarting. This is a laptop and it's shared in the field by several people. By getting everyone to log into the accounts and turn that feature off, it limited the number of automatic processes that would restart. By opening up Activity Monitor, and first killing launchd for each of these unused accounts, then the rest of the processes, it seems to have cleared that problem up. This system has been through several OS upgrades so it's quite possible some people may not have used this thing since Lion or Mountain Lion were on it. I am, of course, talking about killing launchd associated with people not using the system, not an active version of it.
As far as items 2, 3, and 5 go, any time Safari needs to run some video this problem seems to surface. It doesn't seem to happen with other browsers.