Setting the sticky bit on a file fails in a zone

Question

On initial inspection, the sticky bit on directories seem to be consistent across both the Global zone and local zone. However, they are inconsistent for files. Is this a bug, and if it is how to I raise a defect report?
Excerpt from chmod man page:
If a regular file is not executable and has {stick bit} set, the file is assumed to be a swap file. In this case, the system's page cache will not be used to hold the file's data. If the {stick bit} bit is set on any other file, the results are unspecified.
Solaris 10 update 4 (Global Zone).
# uname -a
SunOS mumble.amtest.com 5.10 Generic_120011-14 sun4v sparc SUNW,Sun-Fire-T1000
# chmod 1777 testfile
# ls -l testfile
-rwxrwxrwt 1 root other 0 Jul 11 14:24 testfile
# chmod 1770 testfile
# ls -l testfile
-rwxrwx--T 1 root other 0 Jul 11 14:24 testfile
# chmod 1000 testfile
# ls -l testfile
---------T 1 root other 0 Jul 11 14:24 testfile
Solaris 10 update 4 (Local Zone)
# uname -a
SunOS qatamos-z1 5.10 Generic_120011-14 sun4v sparc SUNW,Sun-Fire-T1000
# chmod 1777 testfile
# ls -l testfile
-rwxrwxrwx 1 root other 10 Jul 10 14:59 testfile
# chmod 1770 testfile
# ls -l testfile
-rwxrwx--- 1 root other 10 Jul 10 14:59 testfile
# chmod 1000 testfile
# ls -l testfile
---------- 1 root other 10 Jul 10 14:59 testfile

Answer 1

It isn't the fact that the bit isn't set. I guess the biggest complaint is that there is no error when trying to set the bit.
chmod returns success, even though it failed to set the bit.
Normally, if someone does not have enough privileges to modify permissions on a file, an error is returned.