Resolver keeps orphant dependency branches

I use the resolver in bnd. Thus this might be an issue of the bnd way of using it, but I will adress it here first.

It appears that the resolver keeps dependency branches of dependences it once considered variable, but through out at a certain point. 

I have project that uses mongo. Mongo itself uses bson and the mongo driver bundle brings all the necessary classes with proper exports and imports. The workspace repositories contain however dependencies for our EMF BSON support using bson4jackson and jackson.

If I resolve with only the mongo related components as requirements, the jackson and bson4jackson dependencies creep in. If I look at the reason (see screenshot), it tells me that `org.gecko.emf.osgi.bson` is the cause. This bundle however is not part of the resolve result. 

If I actively deny list this bundle (and `org.gecko.emf.osgi.json` for some reason), they don't appear.