Reason for this behavior change is how mysqld_safe is invoked by the startup script.
Version 5.6.37 for Trusty/Xenial:
"${PERCONA_PREFIX}"/bin/mysqld_safe > /dev/null 2>&1 &
Version 5.7.19 for Trusty/Xenial:
su - mysql -s /bin/bash -c "mysqld_safe > /dev/null &"
So for version 5.7 mysqld_safe script invoked as mysql user and cannot change any limits by itself.
This change existed in upstream since, at least, version 5.7.9 (first 5.7 GA version).
Reason for this behavior change is how mysqld_safe is invoked by the startup script.
Version 5.6.37 for Trusty/Xenial:
"${PERCONA_ PREFIX} "/bin/mysqld_ safe > /dev/null 2>&1 &
Version 5.7.19 for Trusty/Xenial:
su - mysql -s /bin/bash -c "mysqld_safe > /dev/null &"
So for version 5.7 mysqld_safe script invoked as mysql user and cannot change any limits by itself.
This change existed in upstream since, at least, version 5.7.9 (first 5.7 GA version).