Description:
I have installed both: GNOME and KDE desktop environments, allowing users to choose one of them. One of the gnome's dependencies is blueman - a Bluetooth manager, default for gnome. It installs an autostart "shortcut": /etc/xdg/autostart/blueman.desktop. However, it autostarts for every session: both GNOME and KDE. Since KDE has its own bluetooth manager (kbluetooth), there is no need to use blueman for KDE session. Moreover, blueman starts a lot of its gnome dependencies, like gvfsd and its stuff.

There is a quick fix available: /etc/xdg/autostart/blueman.desktop should contain something like this:
OnlyShowIn=GNOME;XFCE;
This prevents blueman autostaring in KDE, allowing to get rid of the GNOME stuff in KDE session.

I am not sure this should be reported upstream - please let me know if you are not going to fix it just for Arch. But - in general - there is not a lot of freaks using both GNOME and KDE on the same PC, so installing blueman in 99% cases means someone wants to use it regardless of desktop environment. It's up to you to decide.

Additional info:
* blueman-1.21

Steps to reproduce:
* install kde
* install blueman
* start kde session