I don't see one being able to get rid of that dependency - nor is it a bad thing, not every Resource implementation is going to be constructed from primitive types.  

There are couple things that make his PR a bit confusing, the name is one.  Right now we have 

public class BatchJobExecutionInfo extends ResourceSupport

This should be

public class BatchJobExecutionInfoResource extends ResourceSupport

Then the issue would be do we also create a BatchJobExecutionInfoResourceAssembler and a new BatchJobExecutionInfo class that doesn't inherit from ResourceSupport.  To be honest, I'm not sure what adding those two new classes would get.  Perhaps, in the interest of time, we can just do this renaming and then come back in another iteration to deal with having a ResourceAssembler and BatchJobExecutionInfo class that doesn't inherit from ResourceSupport.