Version 15.2(1)E on 4900M globally enables ip device tracking and can't remove it

Question

We wanted to upgrade our 4900M devices to version 15.2(1)E due to some feature for ipv6.
Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500e-ENTSERVICESK9-M), Version 15.2(1)E, RELEASE SOFTWARE (fc3)
After the upgrade we started to get error-reports from users that they got duplicate-ip error messages.
The violating mac-address turned out to be from the upgraded  switch where the vlan passed through, but the switch itself does not  have an ip-address in that vlan. The devices reporting the error are also not connected to the switch.
We were a bit puzzled about that but then we found that after the upgrade there is an extra line in the config
"ip device tracking"
which is something we do not use, but we can't seem to remove it.
switchname(config)#no ip device tracking
% IP device tracking is disabled at the interface level by removing the relevant configs
however, there is no config defined on interface level, and even tried to disable it on interface level anyway, it makes no difference.
All the interfaces are enabled for ip device tracking as well, and we are also not able to remove an interface.
Searching the web we find that ip device tracking has been known to be responsable for duplicate-ip errors.
I have now configured the "workaround"
ip device tracking probe delay 10
Don't know yet if it will make a difference but i don't want to finetune or configure a feature we don't use, i would like to disable something which shouldn't have been there in the first place.
Any thoughts on how to disable the ip device tracking?

Answer 1

Thanks John,
after configuring "no macro auto monitor" all the physical interfaces are removed from being IPDT enabled.
On the 4500-x switch in the lab that even meant all the interfaces and IPDT was disabled globally as well.
On our production switch (4900M) i seemed to see some different behaviour.
At first when i tried it, all the physical interfaces where "nmsp attachment suppress" was in place were removed from the IPDT. 
After some investigation it turns out i also had placed globally "nmsp enable", since the suppress didn't seem to do anything.
Having "nmsp enabled" is thus a feature that makes ipdt active on a port, but you can counter it by setting nmsp attachment suppress.
In my case, since i originally didn't have nmsp enabled, i just disabled it again globally.
The "macro auto monitor"  is apparently, as you point out, also a feature that will enable IPDT on a port.
Turning it off disabled IPDT on all the physical interfaces.
Which means i am close to a workaround but not quite, because it doesn't seem to work for the active port-channels.
It's a bit weird for the port-channels at first sight.
- configured port-channel, state not-connected -> not IPDT enabled
- configured port-channel, state up -> IPDT enabled
- if I shut down a port-channel , so state admin down -> the port-channel as well as the physical member-interfaces are made IPDT enabled. (which considering they are down shouldn't matter much, it is just odd)
Any thoughts on IPDT with port-channels?