This is working by design.  It was decided that treating these records as constituents in these instances allows users to set up relationships and households using existing functionality.  Typically when performing a search though, users would enter names, addresses, etc. that would identify a specific constituent record and not a non-constituent, so this should not be a problematic issue.