Isilon - smartconnect best practices

Community,

I am working for a customer that has Isilon clusters that have multiple smartconnect pools configured under one subnet.  The problem is that there is only one smart connect service IP that can be used to managed these 3 pools configured under it.  Something doesn't seem right about this to me.  2 of the pools have IPs configured on the same subnet and one pool has a totally different subnet all together.   I think that all 3 pools regardless of their being on the same subnet should be configured under different subnet pools so that they can all be assigned with their own smartconnect IP.  One pool is managing IPs for NFS, another pool for SMB, and the 3 pool is for management, yet there all under the same smart connect zone.  I think they all should be self contained in their own zones.  What is your take?