If you do not have access to the code from the applications accessing your database, using the Profiler over a reasonable period of time, as commented by @nelson-casanova, is your best option.
If you do have access to the application code, check there. Also check the definition of any stored procedures, functions, or other views.
I presume you need the column removed for security reasons? If so, perhaps you can modify your view to use IS_SRVROLEMEMBER and return those columns only when authorized? Copy your view and name it 'original_view', copy your view and edit your columns then and name it 'modified_view. Now edit your view and call the new views:
IF IS_SRVROLEMEMBER ('role_view_all') = 1
select * from original_view;
ELSE IF IS_SRVROLEMEMBER ('role_view_all') = 0
select * from modified_view;
If there is an application that you missed in your Profiler run, you can temporarily add that application's user(s) to the 'role_view_all' role, while developers sort out a workaround or fix their queries.