Stray module in service program

I have a service program with a couple dozen modules that I intended it to have, and one extra one that the CRTSRVPGM thought I should have "just because".
I really want that other one to be in another service program instead, and I don't want it to be in both.
This is a project I've been working on for awhile. Over the months, I've changed my strategy of what-belongs-where. The "WRTSOMEMOS" module should be in the TFSORDERS service program - it may have been in the NEONOVAAPI service program at one time.

I delete the NEONOVAAPI service program.
I create the TFSORDERS service program with MODULE(WRTSOMEMOS + a couple others that belong there).
I verify TFSORDERS now has WRTSOMEMOS, and that the TFSORDERS *BNDDIR has the current copy WRTSOMEMOS module. (OK so far).
I recompile the module source members that have an H-spec BNDDIR(TFSORDERS) just in case that matters, and I delete the four programs in my development library that have that H-spec, just in case that matters.
I create the NEONOVAAPI service program, specifying the modules that should be there, and specify EXPORT(*SRCFILE). [the export list in the QSRVSRC member does NOT include WRTSOMEMOS].
I run DSPSRVPGM NEONOVAAPI DETAIL(*MODULE) and see that WRTSOMEMOS is there (?).

Okay, I try this again. I delete and recreate the NEONOVAAPI *srvpgm, this time with EXPORT(*ALL). Still has the WRTSOMEMOS module.
And again, after deleting the WRTSOMEMOS module. CRTSRVPGM fails, because it can't find the module I didn't want it to find.

I suspect there might be an object (in my library or elsewhere?) that has some connection to that module, but I don't know what or where.

Any ideas? V7.1 here, and we don't use a commercial CMS.

Thanks.
Michael Koester